System and method for performing transmission cancellation indication monitoring

ABSTRACT

Various aspects include a method of providing, by a network to a UE device, a transmission grant. The method includes initiating a process to provide the transmission grant for a transmission within a particular time. The method includes verifying that there is no cancellation indication that overlaps the particular time. The method includes providing, based on the verification, the transmission grant to the UE device. The method includes determining whether there is no transmission that overlaps with a cancellation window associated with a monitoring occasion, and based on the determination, skipping the monitoring occasion. Also disclosed a system for providing a transmission grant to the UE device.

RELATED APPLICATION DATA

This application claims the benefit of U.S. Provisional Application Ser.No. 62/875,789, filed on Jul. 18, 2019, which is hereby incorporated byreference.

TECHNICAL AREA

The present embodiments relate to wireless network systems, and moreparticularly, to systems and methods for performing transmissioncancellation indication monitoring associated with a user equipment (UE)and a network.

BACKGROUND

Cancellation indication (CI) is an indication from a network to a UE tocancel a UE transmission including time and frequency resources that thenetwork has previously allocated for the UE. The reason behind such acancellation is to free up some resources for other users that havehigher priority information to transmit, e.g., for ultra-reliable andlow-latency communication (URLLC).

To perform this cancellation, the UE first needs to receive a CI, whichmay be delivered via a physical downlink control channel (PDCCH). Toreceive via the PDCCH, the UE may monitor potential PDCCH transmissionsat each monitoring occasion (MO). Existing PDCCH monitoring techniquesin New Radio (NR) do not consider the relationship between dynamic grantand cancellation indication. Since a cancellation operation is performedto accommodate a higher priority transmission having an urgent need fortransmission, an MO of a CI naturally tends to become quite frequent,and a procedure of CI monitoring can become burdensome for the UE and/orthe network.

BRIEF SUMMARY

Various embodiments of the disclosure include a method of providing, bya network to a UE device, a transmission grant. The method may includeinitiating a process to provide the transmission grant for atransmission within a particular time. The method may include verifyingthat there is no cancellation indication that overlaps the particulartime. The method may include providing, based on a verification thatthere is no cancellation indication that overlaps, the transmissiongrant to the UE device.

Some embodiments include a method for reducing processing burden withina UE device. The method may include determining, by a cancellationindication monitoring logic section of the UE device, whether there isno transmission that overlaps with a cancellation window associated witha monitoring occasion. The method may include, based on determining thatthere is no transmission that overlaps with the cancellation window,skipping the monitoring occasion.

Some embodiments include a system, comprising a UE device and a remoteserver. The remote server can be configured to provide a transmissiongrant for a transmission within a particular time. The remote server canbe further configured to verify that there is no cancellation indicationthat overlaps the particular time. The remote server can further beconfigured to provide, based on a verification that there is nocancellation indication that overlaps, the transmission grant to the UEdevice.

Some embodiments include a cancellation monitoring logic section of a UEdevice. The cancellation monitoring logic section can be configured todetermine whether there is no transmission that overlaps with acancellation window associated with a monitoring occasion. Thecancellation monitoring logic section can be configured to, based ondetermining that there is no transmission that overlaps with thecancellation window, skip the monitoring occasion.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and additional features and advantages of the presentdisclosure will become more readily apparent from the following detaileddescription, made with reference to the accompanying figures, in which:

FIG. 1 illustrates a system including a network and one or more UEdevices each having a cancellation indication monitoring logic sectionin accordance with some embodiments disclosed herein.

FIG. 2 illustrates a timing diagram along a time axis including an MOfor a CI, a cancellation window, and other time periods related to acancellation monitoring operation in accordance with some embodimentsdisclosed herein.

FIG. 3 illustrates a timing diagram along a time axis including an MOfor a CI, a cancellation window, and other time periods related to acancellation monitoring operation in accordance with some embodimentsdisclosed herein.

FIG. 4 illustrates a timing diagram along a time axis including an MOfor a CI, a cancellation window, and other time periods related to acancellation monitoring operation in accordance with some embodimentsdisclosed herein.

FIG. 5 is a flow diagram illustrating a technique for providing, by anetwork to a UE device, a transmission grant in accordance with someembodiments disclosed herein.

FIG. 6 is a flow diagram illustrating another technique for providing,by a network to a UE device, a transmission grant in accordance withsome embodiments disclosed herein.

FIG. 7 is a flow diagram illustrating a technique for establishing acancellation window and a grant window in accordance with someembodiments disclosed herein.

FIG. 8 is a flow diagram illustrating a technique for not providing, bya network to a UE device, a transmission grant in accordance with someembodiments disclosed herein.

FIG. 9 is a flow diagram illustrating a technique for skipping amonitoring occasion in accordance with some embodiments disclosedherein.

FIG. 10 is a flow diagram illustrating another technique for skipping amonitoring occasion in accordance with some embodiments disclosedherein.

FIG. 11 is a flow diagram illustrating yet another technique forskipping a monitoring occasion in accordance with some embodimentsdisclosed herein.

FIG. 12 is a flow diagram illustrating still another technique forskipping a monitoring occasion in accordance with some embodimentsdisclosed herein.

FIG. 13 is a flow diagram illustrating a technique for determiningwhether or not to send a cancellation indication in accordance with someembodiments disclosed herein.

DETAILED DESCRIPTION

Reference will now be made in detail to embodiments disclosed herein,examples of which are illustrated in the accompanying drawings. In thefollowing detailed description, numerous specific details are set forthto enable a thorough understanding of the inventive concept. It shouldbe understood, however, that persons having ordinary skill in the artmay practice the inventive concept without these specific details. Inother instances, well-known methods, procedures, components, circuits,and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another. For example, a first interface could be termed asecond interface, and, similarly, a second interface could be termed afirst interface, without departing from the scope of the inventiveconcept.

The terminology used in the description of the inventive concept hereinis for the purpose of describing particular embodiments only and is notintended to be limiting of the inventive concept. As used in thedescription of the inventive concept and the appended claims, thesingular forms “a”, “an” and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willalso be understood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. The components and featuresof the drawings are not necessarily drawn to scale.

Embodiments disclosed herein provide a CI monitoring method and systemin which a UE can reduce processing burden. Based on the CI monitoringconfiguration and the corresponding scheduling described herein, certainMOs can be skipped, which can reduce a UE's processing burden.

A CI is an indication from a network to a UE to cancel the UE'stransmission including time and frequency resources that the network haspreviously allocated for the UE. To perform this cancellation, the UEmay first receive the CI, which may be delivered via the PDCCH. Toreceive via the PDCCH, the UE may monitor potential PDCCH transmissionsat each MO.

Since a cancellation operation is performed to accommodate higherpriority transmissions having an urgent need for transmission, an MO ofa CI naturally tends to become quite frequent and burdensome.Accordingly, some embodiments disclosed herein include a system andmethod for performing CI monitoring in which the UE can reduce suchprocessing burden. For example, the system and method can ensure thatthe UE does not receive a grant for a transmission whose starting pointin time is the same as or later than a starting point in time of thecorresponding CI. The starting point in time of the CI may match thestarting point in time of the MO, and the ending point in time of the CImay match the ending point in time of the MO. Thus the CI and MO timingwindows may overlap in some or most cases.

FIG. 1 illustrates a system 100 including a network 102 and one or moreUE devices (e.g., 105 a, 105 b, 105 c) each having a cancellationindication monitoring logic section (e.g., 110 a, 110 b, 110 c) inaccordance with some embodiments disclosed herein. The network 102 mayinclude a cellular network or other type of wireless network. The UEdevices may include, for example, a mobile computer 105 a, a smarttablet 105 b, a smart mobile phone 105 c, or the like. The one or moreUE devices (e.g., 105 a, 105 b, 105 c) may be communicatively coupled toone or more remote servers (e.g., 115) via the network 102. The network102 may include one or more towers such as cell towers 120 a and 120 bto facilitate transmission of information between the one or more UEdevices (e.g., 105 a, 105 b, 105 c) and the network 102. The network 102may include the one or more remote servers 115. The cancellationindication monitoring logic section (e.g., 110 a, 110 b, 110 c) may beembedded within each of the corresponding UE devices (e.g., 105 a, 105b, 105 c). The cancellation indication monitoring logic section (e.g.,110 a, 110 b, 110 c) may be embodied as software, firmware, hardware, orany suitable combination thereof.

FIG. 2 illustrates a timing diagram 200 along a time axis 202 includingan MO 205 for a CI (e.g., 220), a cancellation window 210, and othertime periods (e.g., T₁ and T₂) related to a cancellation monitoringoperation in accordance with some embodiments disclosed herein.

Given a particular MO 205 for a CI (e.g., 220), the cancellation window210 of a potential cancellation region may be determined, which isassociated with the particular MO 205. In other words, based on a CI(e.g., 220) detected within the MO 205, one or more scheduledtransmissions 235 that would otherwise occur within the cancellationwindow 210 may be cancelled. A starting point in time of thecancellation window 210 may be at 225, which may be a distance of T₁from an ending point 230 of the MO 205, as shown in FIG. 1. The timeperiod T₁ can be determined based on a processing time of the CI 220,which can include a decoding time of the CI 220, and/or preparation timeof a cancellation operation of the one or more scheduled transmissions235.

T₁ may define an earliest possible point in time at which the one ormore cancellation indication monitoring logic sections (e.g., 110 a, 110b, 110 c) of the one or more UE devices (e.g., 105 a, 105 b, and 105 cof FIG. 1) can perform a cancellation operation in response to the CI220 detected during the MO 205. An ending point 240 in time of thecancellation window 210 may be based on how far ahead a cancellation canbe indicated, and this may be dependent on the design of thecancellation indication signaling. In some embodiments, a length of thecancellation window 210 may be based on a length of the MO 205. In someembodiments, the length of the cancellation window 210 is at least aslong as the length of the MO 205.

In some embodiments, the cancellation window 210 may begin at an endingpoint 225 of T₁ from the ending point 230 of the MO 205. The one or morescheduled transmissions 235 associated with the one or more UE devices(e.g., 105 a, 105 b, and 105 c of FIG. 1) that fall within thecancellation window 210 may be cancelled based on the CI 220 detectedduring the corresponding MO 205. T₁ may be the time needed to process acancellation operation based on the CI 220 detected during the MO 205,which can include decoding time of the CI 220 and preparation time ofthe cancellation operation. In some embodiments, T₁ is a variable timevalue that may be dependent on one or more characteristics of the CI220.

In some embodiments, the ending point 240 of the cancellation window 210may depend on a period “P” (e.g., a gap) of the MO 205. One possiblevalue of a length of the cancellation window 210 may be equal to “P.”

In some embodiments, the disclosed cancellation system and method canensure that the network 102 does not provide a dynamic transmissiongrant (e.g., 245) at the same time as, or after, the network 102determines to send a CI (e.g., 220). Accordingly, the one or more UEdevices (e.g., 105 a, 105 b, and 105 c of FIG. 1) need not receive adynamic transmission grant (e.g., 245) for a transmission falling withinthe cancellation window 210 after the MO 205 starts.

In some embodiments, the cancellation system and method disclosed hereinensures that an ending point 255 of a dynamic transmission grant (e.g.,245), i.e., a last possible time of reception by the one or more UEdevices (e.g., 105 a, 105 b, and 105 c of FIG. 1) of the dynamictransmission grant 245, is at least T₂ before a starting point 250 ofthe MO 205. T₂ may be a decoding time of uplink (UL) grant or downlink(DL) grant scheduling acknowledgment (ACK) and/or negativeacknowledgment (NACK) associated with a physical uplink control channel(PUCCH). In other words, the one or more cancellation indicationmonitoring logic sections (e.g., 110 a, 110 b, 110 c) of the one or moreUE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) need not expect toreceive a transmission grant (e.g., 245) whose ending point (e.g., 255)is later than point 260 in time (i.e., T₂ before the starting point 250of the MO 205) for a transmission (e.g., 235) falling within thecancellation window 210. In some embodiments, no downlink controlinformation (DCI) incurring UL transmission overlapping with thecancellation window 210 is expected after the point 250 in time. In someembodiments, there is no MO for a UL grant within the time period T₂.

FIG. 3 illustrates a timing diagram 300 along a time axis 302 includingan MO 305 for a CI (e.g., 320), an MO 308 for a CI (e.g., 328), acancellation window 310, and other time periods (e.g., T₁) related to acancellation monitoring operation in accordance with some embodimentsdisclosed herein.

One possible candidate of a length of a cancellation window 310 startsat an ending point 325 of T₁ after an ending point 330 of the MO 305 forthe CI (e.g., 320), and ends at an ending point 360 of T₁ after anending point 365 of a next MO 308 for the CI (e.g., 328) as shown inFIG. 2. In some embodiments, a length of the cancellation window 310 maydepend on a period “P” (e.g., a gap) of the MO 308. One possible valueof a length of the cancellation window 210 may be equal to “P.”

In addition, processing burden of the one or more UE devices (e.g., 105a, 105 b, and 105 c of FIG. 1) for monitoring for the CI (e.g., 320,328) may be reduced based on there being no UL transmission (e.g., 235of FIG. 2) scheduled that is overlapping with the correspondingcancellation window 310. The one or more cancellation indicationmonitoring logic sections (e.g., 110 a, 110 b, 110 c) of the one or moreUE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) can determine theexistence of a semi-static transmission state. Accordingly, the one ormore cancellation indication monitoring logic sections (e.g., 110 a, 110b, 110 c) of the one or more UE devices (e.g., 105 a, 105 b, and 105 cof FIG. 1) can control their scheduling request (SR) transmission.Hence, the one or more cancellation indication monitoring logic sections(e.g., 110 a, 110 b, 110 c) of the one or more UE devices (e.g., 105 a,105 b, and 105 c of FIG. 1) can skip the MO (e.g., 305, 308) for the CI(e.g., 320, 328) based on the determination that there is notransmission potentially overlapping with the cancellation window 310associated with the corresponding MO (e.g., 305, 308). Thus, the one ormore cancellation indication monitoring logic sections (e.g., 110 a, 110b, 110 c) of the one or more UE devices (e.g., 105 a, 105 b, and 105 cof FIG. 1) can determine that there is no scheduled transmission (e.g.,235 of FIG. 2) that overlaps the cancellation window 310, and activelyskip the corresponding MO 308. In other words, the one or more UEdevices (e.g., 105 a, 105 b, and 105 c of FIG. 1) need not expend anyprocessing cycles doing any monitoring for the CI 328 during the MO 308.

FIG. 4 illustrates a timing diagram 400 along a time axis 402 includingan MO 405 for a CI (e.g., 420), a cancellation window 410, and othertime periods (e.g., T₁ and T₂) related to a cancellation monitoringoperation in accordance with some embodiments disclosed herein.

In some embodiments, one or more dynamic transmissions 435, which arewithin the cancellation window 410 can be scheduled before and/or afterthe MO 405 of the CI (e.g., 420). For example, a UL grant and/or a DLgrant scheduling ACK/NACK 422 via a PUCCH 424 may be provided after astarting point 450 of the MO 405 of the CI (e.g., 420). In someembodiments, the network 102 is at least informed of a cancellation 426that overlaps with the one or more dynamic transmissions 435.

Since such a transmission (i.e., a dynamic transmission 435 thatoverlaps with the cancellation 426) will anyway be cancelled, thenetwork 102 need not provide the corresponding UL and/or DL grant 422.In some embodiments, the dynamic UL and/or DL grant 422 is not providedby the network 102 after the CI 420 of the corresponding transmission(e.g., 435) is provided. Put differently, the network 102 need not granta transmission when the network 102 possesses information that there isa CI 420 for that transmission. A starting point of a dynamic grant(e.g., 422) should not be the same or later than a starting point of theCI 420. In other words, the one or more cancellation indicationmonitoring logic sections (e.g., 110 a, 110 b, 110 c) of the one or moreUE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) need not expect toreceive a grant whose starting point is the same or later than thestarting point of the CI 420 when the corresponding transmission (e.g.,435) is cancelled (e.g., at 426) by the CI 420. Put differently, the oneor more cancellation indication monitoring logic sections (e.g., 110 a,110 b, 110 c) of the one or more UE devices (e.g., 105 a, 105 b, and 105c of FIG. 1) can infer that a transmission grant will not be receivedwhose starting point is the same or later than the starting point of theCI 420 when the corresponding transmission (e.g., 435) is cancelled(e.g., at 426) by the CI 420. Based on the inference, the one or morecancellation indication monitoring logic sections (e.g., 110 a, 110 b,110 c) of the one or more UE devices (e.g., 105 a, 105 b, and 105 c ofFIG. 1) can cause a monitoring occasion to be skipped.

In a case where a UL grant (e.g., 422) arrives considerably later thanthe CI 420, then the one or more cancellation indication monitoringlogic sections (e.g., 110 a, 110 b, 110 c) of the one or more UE devices(e.g., 105 a, 105 b, and 105 c of FIG. 1) may have already decoded theCI 420 and recognized or otherwise determined the cancellation 426before decoding the UL grant (e.g., 422). In this case, the one or moreUE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) may receive the ULgrant (e.g., 422) corresponding to one or more already-cancelledorthogonal frequency-division multiplexing (OFDM) symbols. Hence, whenthe starting point of the dynamic grant (e.g., 422) is not the same orlater than the starting point of the CI 420, then the one or more UEdevices (e.g., 105 a, 105 b, and 105 c of FIG. 1) need not expect to bescheduled to transmit in the cancelled symbols indicated by the CI 420.Put differently, when the starting point of the dynamic grant (e.g.,422) is not the same or later than the starting point of the CI 420,then the one or more UE devices (e.g., 105 a, 105 b, and 105 c ofFIG. 1) can infer that the cancelled symbols indicated by the CI 420will not be scheduled to transmit. Based on the inference, the one ormore cancellation indication monitoring logic sections (e.g., 110 a, 110b, 110 c) of the one or more UE devices (e.g., 105 a, 105 b, and 105 cof FIG. 1) can cause a monitoring occasion to be skipped.

In some embodiments, the one or more UE devices (e.g., 105 a, 105 b, and105 c of FIG. 1) do not expect to receive (e.g., the UE devices can makean inference that they will not receive) a PDCCH carrying UL grant(e.g., 245, 422, 428) including an ending symbol no earlier than a lastsymbol of a PDCCH carrying DCI with the CI 420 when the correspondingtransmission (e.g., 435) is in resource colliding (e.g., at 426) withones indicated by the DCI with the CI 420. In some embodiments, when anending symbol of the PDCCH carrying the UL grant (e.g., 245, 422, 428)is earlier than the last symbol of the PDCCH carrying DCI with the CI420, the DCI with the CI 420 is applicable to the UL grant (e.g., 245,422, 428) scheduling transmission (e.g., 435).

In some embodiments, the one or more UE devices (e.g., 105 a, 105 b, and105 c of FIG. 1) do not expect to receive (e.g., the UE devices can makean inference that they will not receive) a PDCCH carrying UL grant(e.g., 245, 422, 428) including an ending symbol no earlier than a firstsymbol of a PDCCH carrying DCI with the CI 420 when the correspondingtransmission (e.g., 435) is in resource colliding (e.g., at 426) withones indicated by the DCI with the CI 420. In some embodiments, when anending symbol of the PDCCH carrying the UL grant (e.g., 245, 422, 428)is earlier than the first symbol of the PDCCH carrying DCI with the CI420, the DCI with the CI 420 is applicable to the UL grant (e.g., 245,422, 428) scheduling transmission (e.g., 435).

Consider the case where a UL and/or DL grant scheduling ACK/NACK 428 viathe PUCCH 424 is provided before the MO 405 of the CI 420. In this case,the one or more UE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) canknow of the existence of UL grant (e.g., 428) as long as thecorresponding decoding is finished before the MO 405 of the CI 420. Thetime for decoding can be equal to T₂ as shown in FIG. 4. Accordingly,the one or more UE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) canskip monitoring the MO 405 of the CI 420 when there is no other PDCCHMO, which can provide a DL and/or a UL grant between a point 460 and thestarting point 450 of the MO 405 of the CI 420. In other words, the oneor more UE devices (e.g., 105 a, 105 b, and 105 c of FIG. 1) can skipmonitoring the MO 405 of the CI 420 when there is no other PDCCH MO,which can provide a DL and/or a UL grant within the T₂ time period.

One possible value of T₂ can be N₂, which may be defined in an NRspecification. Hence, in some embodiments, a dynamic grant (e.g., 428)may be provided by the network 102 at least T₂ before the CI 420 (i.e.,before the starting point 450 of the MO 405) of the corresponding ULtransmission (e.g., 435). An ending point of the dynamic grant (e.g.,428) should not be later than T₂ before the starting point of the CI 420(i.e., before the starting point 450 of the MO 405). Put differently, anending point of the dynamic grant (e.g., 428) should not be later thanthe point 460 in time. In other words, the one or more UE devices (e.g.,105 a, 105 b, and 105 c of FIG. 1) need not expect to receive a grantwhose ending point is later than T₂ before the starting point 450 of theMO 405 when the corresponding transmission (e.g., 435) is cancelled bythe CI 420.

In some embodiments, the network 102 may provide a transmission grant(e.g., 428) for a transmission (e.g., 435) to the one or more UE devices(e.g., 105 a, 105 b, and 105 c of FIG. 1). The network 102 may initiatea process to provide the transmission grant 428 for a transmission(e.g., 435) within a particular time. The network 102 may verify thatthere is no CI (e.g., 420) that overlaps with the particular time. Basedon the verification that there is no overlap, the network 102 mayprovide the transmission grant 428 to the one or more UE devices (e.g.,105 a, 105 b, 105 c). In other words, the network 102 may verify that acancellation 426 indicated by the CI 420 does not overlap with aparticular time in which a scheduled transmission 435 is scheduled, andbased on that verification, the network 102 may provide the transmissiongrant 428. Otherwise, the network 102 may not provide the transmissiongrant 428 so that processing resources may be preserved. The particulartime may be the cancellation window 410. Thus, the network 102 mayinitiate the process to provide the transmission grant 428 for thetransmission 435 at a time falling within the cancellation window 410.

In some embodiments, the network 102 may determine a grant window 470 inwhich the transmission grant 428 for the transmission 435 falling withinthe cancellation window 410 can be provided to the one or more UEdevices (e.g., 105 a, 105 b, and 105 c of FIG. 1). In some embodiments,the network 102 does not provide any grant outside of the grant window.The network 102 may verify that the transmission grant 428 falls withinthe grant window 470. The network 102 may provide, based on theverification, the transmission grant 428 to the one or more UE devices(e.g., 105 a, 105 b, 105 c).

In some embodiments, the cancellation window 410 is associated with theMO 405, which is associated with the one or more UE devices (e.g., 105a, 105 b, and 105 c of FIG. 1). The cancellation window 410 may includea starting point 425 at a time T₁ following an ending point 430 of theMO 405. The time T₁ may be based on a time needed by the one or more UEdevices (e.g., 105 a, 105 b, 105 c) to process a cancellation (e.g.,426) of the transmission grant (e.g., 428).

In some embodiments, the grant window 470 includes an ending point 460at a time T₂ before a starting point 450 of the MO 405. The time T₂ maybe based on a time needed by the one or more UE devices (e.g., 105 a,105 b, 105 c) for processing the transmission grant 428. The network 102may receive an indication of the time T₂ from the one or more UE devices(e.g., 105 a, 105 b, 105 c). In other words, the one or more UE devices(e.g., 105 a, 105 b, 105 c) may provide the T₂ value to the network 102.

FIG. 5 is a flow diagram 500 illustrating a technique for providing, bya network (e.g., 102 of FIG. 1) to a UE device (e.g., 105 a, 105 b, and105 c of FIG. 1), a transmission grant in accordance with someembodiments disclosed herein. At 505, a process is initiated to providethe transmission grant for a transmission within a particular time. At510, a verification can be performed that there is no cancellationindication that overlaps the particular time. At 515, based on averification that there is no cancellation indication that overlaps, thenetwork can provide the transmission grant to the UE device.

FIG. 6 is a flow diagram 600 illustrating another technique forproviding, by a network (e.g., 102 of FIG. 1) to a UE device (e.g., 105a, 105 b, and 105 c of FIG. 1), a transmission grant in accordance withsome embodiments disclosed herein. At 605, a process may be initiated toprovide the transmission grant for a transmission at a time fallingwithin a cancellation window. At 610, a grant window may be determinedin which the transmission grant for the transmission falling within thecancellation window can be provided to the UE device. In someembodiments, the network does not provide any transmission grant outsideof the grant window. At 615, the transmission grant may be verified tofall within the grant window. At 620, based on a verification that thetransmission grant falls within the grant window, the transmission grantmay be provided to the UE device.

FIG. 7 is a flow diagram 700 illustrating a technique for establishing acancellation window (e.g., 210, 310, 410) and a grant window (e.g., 470)in accordance with some embodiments disclosed herein. At 705, acancellation window can be associated with a monitoring occasion. At710, the monitoring occasion can be associated with a UE device (e.g.,105 a, 105 b, 105 c). At 715, a starting point of the cancellationwindow can be set at a time T₁ following an ending point of themonitoring occasion, the time T₁ being based on a time needed by the UEdevice to process a cancellation of the transmission grant. At 720, anending point of a grant window can be set at a time T₂ before a startingpoint of the monitoring occasion, the time T₂ being based on a timeneeded by the UE device for processing the transmission grant. Thenetwork can receive an indication of the time T₂ from the UE device.

FIG. 8 is a flow diagram 800 illustrating a technique for not providing,by a network (e.g., 102) to a UE device (e.g., 105 a, 105 b, 105 c), atransmission grant in accordance with some embodiments disclosed herein.At 805, a process can be initiated to provide a transmission grant for atransmission within a particular time. At 810, a verification can beperformed to verify that there is a cancellation indication thatoverlaps with the particular time. At 815, based on the verificationthat there is the cancellation indication that overlaps, thetransmission grant can be not provided to the UE device.

FIG. 9 is a flow diagram 900 illustrating a technique for skipping an MO(e.g., 205, 305, 308, 405) in accordance with some embodiments disclosedherein. At 905, a cancellation indication monitoring logic section ofthe UE device (e.g., 105 a, 105 b, 105 c) can determine whether there isno transmission that overlaps with a cancellation window associated witha monitoring occasion. At 910, based on determining that there is notransmission that overlaps with the cancellation window, the monitoringoccasion can be skipped by the UE device.

FIG. 10 is a flow diagram 1000 illustrating another technique forskipping an MO (e.g., 205, 305, 308, 405) in accordance with someembodiments disclosed herein. At 1005, a network (e.g., 102) can ensurethat an ending point of a transmission grant is at least a time T₂before a starting point of the monitoring occasion, the time T₂ beingbased on a time needed by the UE device for processing the transmissiongrant. At 1010, a cancellation indication monitoring logic section ofthe UE device can infer that the transmission grant will not be receivedwhose ending point is later than the time T₂ before the starting pointof the monitoring occasion. At 1015, based on an inference that thetransmission grant will not be received whose ending point is later thanthe time T₂ before the starting point of the monitoring occasion, themonitoring occasion can be skipped.

FIG. 11 is a flow diagram 1100 illustrating yet another technique forskipping a monitoring occasion (e.g., 205, 305, 308, 405) in accordancewith some embodiments disclosed herein. At 1105, a cancellationindication monitoring logic section (e.g., 110 a, 110 b, 110 c) of a UEdevice (e.g., 105 a, 105 b, 105 c), that a transmission grant (e.g.,245, 422, 428) will not be received whose starting point is the same orlater than a starting point of a cancellation indication (e.g., 220,320, 328, 420). At 1110, based on the inferring that the transmissiongrant (e.g., 245, 422, 428) will not be received whose starting point isthe same or later than the starting point of the cancellation indication(e.g., 220, 320, 328, 420), the cancellation indication monitoring logicsection of the UE device may cause a monitoring occasion (e.g., 205,305, 308, 405) to be skipped.

FIG. 12 is a flow diagram 1200 illustrating still another technique forskipping a monitoring occasion (e.g., 205, 305, 308, 405) in accordancewith some embodiments disclosed herein. At 1205, a cancellationindication monitoring logic section (e.g., 110 a, 110 b, 110 c) of a UEdevice (e.g., 105 a, 105 b, 105 c) may infer that cancelled symbolsindicated by the cancellation indication (e.g., 220, 320, 328, 420) willnot be scheduled to transmit when the starting point of the transmissiongrant (e.g., 245, 422, 428) is not the same or later than the startingpoint of the cancellation indication (e.g., 220, 320, 328, 420). At1210, based on the inferring that the transmission grant (e.g., 245,422, 428) will not be received whose cancelled symbols indicated by thecancellation indication (e.g., 220, 320, 328, 420) will not be scheduledto transmit when the starting point of the transmission grant (e.g.,245, 422, 428) is not the same or later than the starting point of thecancellation indication (e.g., 220, 320, 328, 420), the cancellationindication monitoring logic section of the UE device may cause amonitoring occasion (e.g., 205, 305, 308, 405) to be skipped.

FIG. 13 is a flow diagram 1300 illustrating a technique for determiningwhether or not to send a cancellation indication (e.g., 220, 320, 328,420) in accordance with some embodiments disclosed herein. At 1305, thenetwork can provide a transmission grant (e.g., 245, 422, 428) for anon-urgent UE device (e.g., 105 a, 105 b, 105 c). At 1310, the networkcan determine whether to send the cancellation indication (e.g., 220,320, 328, 420) within a particular monitoring occasion (e.g., 205, 305,308, 405) cancelling an allocation in the transmission grant (e.g., 245,422, 428). At 1315, the network can send the cancellation indication(e.g., 220, 320, 328, 420) within the particular monitoring occasion(e.g., 205, 305, 308, 405) cancelling the allocation in the transmissiongrant (e.g., 245, 422, 428). In some embodiments, the cancellationwindow (e.g., 210, 310, 410) is a potential region, and nothing iscancelled within the cancellation window unless the cancellationindication (e.g., 220, 320, 328, 420) indicating the cancellation isprovided.

It will be understood that any of the components or any combination ofthe components described herein can be used to perform one or more ofthe operations of the flow diagrams of FIGS. 5 through 13. Further, theoperations shown in the flow diagrams are example operations, and mayinvolve various additional steps not explicitly covered. The temporalorder of the operations may be varied.

Reference is now made to FIGS. 1 through 13. A system disclosed hereinmay include a UE device (e.g., 105 a, 105 b, 105 c). The system mayinclude a remote server (e.g., 115) to provide a transmission grant(e.g., 245, 422, 428) for a transmission (e.g., 235, 435) within aparticular time (e.g., 210, 310, 410). The remote server (e.g., 115) canverify that there is no cancellation indication (e.g., 220, 320, 328,420) that overlaps the particular time (e.g., 210, 310, 410). The remoteserver (e.g., 115) can provide, based on a verification that there is nocancellation indication (e.g., 220, 320, 328, 420) that overlaps, thetransmission grant (e.g., 245, 422, 428) to the UE device (e.g., 105 a,105 b, 105 c). The particular time can be a cancellation window (e.g.,210, 310, 410).

The remote server (e.g., 115) can provide the transmission grant (e.g.,245, 422, 428) for the transmission (e.g., 435) at a time falling withinthe cancellation window (e.g., 210, 310, 410). The remote server (e.g.,115) can determine a grant window (e.g., 470) in which the transmissiongrant (e.g., 245, 422, 428) for the transmission (e.g., 435) fallingwithin the cancellation window (e.g., 210, 310, 410) can be provided tothe UE device (e.g., 105 a, 105 b, 105 c). In some embodiments, theremote server (e.g., 115) does not provide any transmission grantoutside of the grant window. The remote server (e.g., 115) can verifythat the transmission grant (e.g., 245, 422, 428) falls within the grantwindow (e.g., 470). The remote server (e.g., 115) can provide, based ona verification that the transmission grant (e.g., 245, 422, 428) fallswithin the grant window (e.g., 470), the transmission grant (e.g., 245,422, 428) to the UE device (e.g., 105 a, 105 b, 105 c).

The cancellation window (e.g., 210, 310, 410) is associated with amonitoring occasion (e.g., 205, 305, 308, 405) that is associated withthe UE device (e.g., 105 a, 105 b, 105 c). The cancellation window(e.g., 210, 310, 410) may include a starting point at a time T₁following an ending point of the monitoring occasion (e.g., 205, 305,308, 405), the time T₁ being based on a time needed by the UE device(e.g., 105 a, 105 b, 105 c) to process a cancellation of thetransmission grant (e.g., 245, 422, 428). In some embodiments, the grantwindow (e.g., 470) includes an ending point at a time T₂ before astarting point of the monitoring occasion (e.g., 205, 305, 308, 405),the time T₂ being based on a time needed by the UE device (e.g., 105 a,105 b, 105 c) for processing the transmission grant (e.g., 245, 422,428). The remote server (e.g., 115) can receive an indication of thetime T₂ from the UE device (e.g., 105 a, 105 b, 105 c).

The remote server (e.g., 115) can verify that there is a cancellationindication (e.g., 220, 320, 328, 420) that overlaps the cancellationwindow (e.g., 210, 310, 410). The remote server (e.g., 115) can notprovide, based on a verification that there is the cancellationindication that overlaps, a transmission grant for a transmission to theUE device (e.g., 105 a, 105 b, 105 c).

A cancellation monitoring logic section (e.g., 110 a, 110 b, 110 c) of aUE device (e.g., 105 a, 105 b, 105 c) can determine whether there is notransmission that overlaps with a cancellation window (e.g., 210, 310,410) associated with a monitoring occasion (e.g., 205, 305, 308, 405).Based on determining that there is no transmission that overlaps withthe cancellation window, the cancellation monitoring logic section(e.g., 110 a, 110 b, 110 c) of a UE device (e.g., 105 a, 105 b, 105 c)can skip the monitoring occasion (e.g., 205, 305, 308, 405).

The cancellation monitoring logic section (e.g., 110 a, 110 b, 110 c)can cause the UE device (e.g., 105 a, 105 b, 105 c) to not expend anyprocessing cycles of the UE device doing any monitoring for acancellation indication during the monitoring occasion (e.g., 205, 305,308, 405). The cancellation monitoring logic section (e.g., 110 a, 110b, 110 c) can infer that the transmission grant (e.g., 245, 422, 428)will not be received whose ending point is later than a time T₂ before astarting point of the monitoring occasion (e.g., 205, 305, 308, 405),the time T₂ being based on a time needed by the UE device for processingthe transmission grant. Based on an inference that the transmissiongrant (e.g., 245, 422, 428) will not be received whose ending point islater than the time T₂ before the starting point of the monitoringoccasion (e.g., 205, 305, 308, 405), cancellation monitoring logicsection (e.g., 110 a, 110 b, 110 c) can cause the monitoring occasion tobe skipped.

The various operations of methods described above may be performed byany suitable means capable of performing the operations, such as varioushardware and/or software component(s), circuits, and/or module(s).

The blocks or steps of a method or algorithm and functions described inconnection with the embodiments disclosed herein may be embodieddirectly in hardware, in a software module executed by a processor, orin a combination of the two. If implemented in software, the functionsmay be stored on or transmitted over as one or more instructions or codeon a tangible, non-transitory computer-readable medium. A softwaremodule may reside in Random Access Memory (RAM), flash memory, Read OnlyMemory (ROM), Electrically Programmable ROM (EPROM), ElectricallyErasable Programmable ROM (EEPROM), registers, hard disk, a removabledisk, a CD ROM, or any other form of storage medium known in the art.

The following discussion is intended to provide a brief, generaldescription of a suitable machine or machines in which certain aspectsof the inventive concept can be implemented. Typically, the machine ormachines include a system bus to which is attached processors, memory,e.g., RAM, ROM, or other state preserving medium, storage devices, avideo interface, and input/output interface ports. The machine ormachines can be controlled, at least in part, by input from conventionalinput devices, such as keyboards, mice, etc., as well as by directivesreceived from another machine, interaction with a virtual reality (VR)environment, biometric feedback, or other input signal. As used herein,the term “machine” is intended to broadly encompass a single machine, avirtual machine, or a system of communicatively coupled machines,virtual machines, or devices operating together. Exemplary machinesinclude computing devices such as personal computers, workstations,servers, portable computers, handheld devices, telephones, tablets,etc., as well as transportation devices, such as private or publictransportation, e.g., automobiles, trains, cabs, etc.

The machine or machines can include embedded controllers, such asprogrammable or non-programmable logic devices or arrays, ApplicationSpecific Integrated Circuits (ASICs), embedded computers, smart cards,and the like. The machine or machines can utilize one or moreconnections to one or more remote machines, such as through a networkinterface, modem, or other communicative coupling. Machines can beinterconnected by way of a physical and/or logical network, such as anintranet, the Internet, local area networks, wide area networks, etc.One skilled in the art will appreciate that network communication canutilize various wired and/or wireless short range or long range carriersand protocols, including radio frequency (RF), satellite, microwave,Institute of Electrical and Electronics Engineers (IEEE) 545.11,Bluetooth®, optical, infrared, cable, laser, etc.

Embodiments of the present disclosure can be described by reference toor in conjunction with associated data including functions, procedures,data structures, application programs, etc. which when accessed by amachine results in the machine performing tasks or defining abstractdata types or low-level hardware contexts. Associated data can be storedin, for example, the volatile and/or non-volatile memory, e.g., RAM,ROM, etc., or in other storage devices and their associated storagemedia, including hard-drives, floppy-disks, optical storage, tapes,flash memory, memory sticks, digital video disks, biological storage,etc. Associated data can be delivered over transmission environments,including the physical and/or logical network, in the form of packets,serial data, parallel data, propagated signals, etc., and can be used ina compressed or encrypted format. Associated data can be used in adistributed environment, and stored locally and/or remotely for machineaccess.

Having described and illustrated the principles of the presentdisclosure with reference to illustrated embodiments, it will berecognized that the illustrated embodiments can be modified inarrangement and detail without departing from such principles, and canbe combined in any desired manner. And although the foregoing discussionhas focused on particular embodiments, other configurations arecontemplated. In particular, even though expressions such as “accordingto an embodiment of the inventive concept” or the like are used herein,these phrases are meant to generally reference embodiment possibilities,and are not intended to limit the inventive concept to particularembodiment configurations. As used herein, these terms can reference thesame or different embodiments that are combinable into otherembodiments.

Embodiments of the present disclosure may include a non-transitorymachine-readable medium comprising instructions executable by one ormore processors, the instructions comprising instructions to perform theelements of the inventive concepts as described herein.

The foregoing illustrative embodiments are not to be construed aslimiting the inventive concept thereof. Although a few embodiments havebeen described, those skilled in the art will readily appreciate thatmany modifications are possible to those embodiments without materiallydeparting from the novel teachings and advantages of the presentdisclosure. Accordingly, all such modifications are intended to beincluded within the scope of this present disclosure as defined in theclaims.

What is claimed is:
 1. A method of providing, by a network to a userequipment (UE) device, a transmission grant, the method comprising:initiating a process to provide the transmission grant for atransmission within a particular time; verifying that there is nocancellation indication that overlaps the particular time; andproviding, based on the verifying that there is no cancellationindication that overlaps, the transmission grant to the UE device. 2.The method of claim 1, wherein the particular time is a cancellationwindow, the method further comprising: initiating the process to providethe transmission grant for the transmission at a time falling within thecancellation window; determining a grant window in which thetransmission grant for the transmission falling within the cancellationwindow can be provided to the UE device, wherein the network does notprovide any transmission grant outside of the grant window; verifyingthat the transmission grant falls within the grant window; andproviding, based on the verifying that the transmission grant fallswithin the grant window, the transmission grant to the UE device.
 3. Themethod of claim 2, wherein: the cancellation window is associated with amonitoring occasion that is associated with the UE device; thecancellation window includes a starting point at a time T₁ following anending point of the monitoring occasion, the time T₁ being based on atime needed by the UE device to process a cancellation of thetransmission grant.
 4. The method of claim 3, wherein the grant windowincludes an ending point at a time T₂ before a starting point of themonitoring occasion, the time T₂ being based on a time needed by the UEdevice for processing the transmission grant.
 5. The method of claim 3,further comprising receiving, by the network, an indication of the timeT₂ from the UE device.
 6. The method of claim 1, wherein: the particulartime is a cancellation window; the cancellation window is associatedwith a monitoring occasion that is associated with the UE device; anending point of the cancellation window is based on a period “P” of themonitoring occasion; and a length of the cancellation window is equal tothe period “P” of the monitoring occasion.
 7. The method of claim 1,wherein: the transmission is a first transmission; the transmissiongrant is a first transmission grant; and the process is a first process;the method further comprising: initiating a second process to provide asecond transmission grant for a second transmission within theparticular time; verifying that there is a cancellation indication thatoverlaps the particular time; and not providing, based on the verifyingthat there is the cancellation indication that overlaps, the secondtransmission grant to the UE device.
 8. The method of claim 7, whereinthe particular time is a cancellation window that is associated with amonitoring occasion that is associated with the UE device.
 9. The methodof claim 1, further comprising: determining whether to send acancellation indication within a monitoring occasion cancelling thetransmission grant; and sending the cancellation indication within themonitoring occasion cancelling the transmission grant.
 10. A method forreducing processing burden within a user equipment (UE) device, themethod comprising: inferring, by a cancellation indication monitoringlogic section of the UE device, that a transmission grant will not bereceived whose starting point is the same or later than a starting pointof a cancellation indication. based on the inferring that thetransmission grant will not be received whose starting point is the sameor later than the starting point of the cancellation indication,skipping a monitoring occasion.
 11. The method of claim 10, furthercomprising: inferring, by the cancellation indication monitoring logicsection of the UE device, that cancelled symbols indicated by thecancellation indication will not be scheduled to transmit when thestarting point of the transmission grant is not the same or later thanthe starting point of the cancellation indication.
 12. The method ofclaim 10, wherein the transmission grant is a physical downlink controlchannel (PDCCH) carrying UL grant, method further comprising: inferring,by the cancellation indication monitoring logic section of the UEdevice, no receipt of the PDCCH carrying UL grant including an endingsymbol no earlier than a last symbol of a PDCCH carrying downlinkcontrol information (DCI) with the cancellation indication when acorresponding transmission is in resource colliding with ones indicatedby the DCI with the cancellation indication.
 13. The method of claim 10,wherein the transmission grant is a physical downlink control channel(PDCCH) carrying UL grant, method further comprising: when an endingsymbol of the PDCCH carrying UL grant is earlier than a last symbol of aPDCCH carrying downlink control information (DCI) with the cancellationindication, applying the DCI with the cancellation indication to a PDCCHcarrying UL grant scheduling transmission.
 14. The method of claim 10,further comprising: determining, by the cancellation indicationmonitoring logic section of the UE device, whether there is notransmission that overlaps with a cancellation window associated withthe monitoring occasion; and based on the determining that there is notransmission that overlaps with the cancellation window, skipping themonitoring occasion.
 15. The method of claim 14, wherein skippingincludes not expending any processing cycles of the UE device doing anymonitoring for the cancellation indication during the monitoringoccasion.
 16. The method of claim 14, further comprising: ensuring thatan ending point of the transmission grant is at least a time T₂ before astarting point of the monitoring occasion, the time T₂ being based on atime needed by the UE device for processing the transmission grant;inferring, by the cancellation indication monitoring logic section ofthe UE device, that the transmission grant will not be received whoseending point is later than the time T₂ before the starting point of themonitoring occasion; and based on the inferring that the transmissiongrant will not be received whose ending point is later than the time T₂before the starting point of the monitoring occasion, skipping themonitoring occasion.
 17. A system, comprising: a user equipment (UE)device; and a remote server configured to provide a transmission grantfor a transmission within a particular time, wherein the remote serveris further configured to: verify that there is no cancellationindication that overlaps the particular time; and provide, based on averification that there is no cancellation indication that overlaps, thetransmission grant to the UE device.
 18. The system of claim 17, whereinthe particular time is a cancellation window, and wherein the remoteserver is further configured to: provide the transmission grant for thetransmission at a time falling within the cancellation window; determinea grant window in which the transmission grant for the transmissionfalling within the cancellation window can be provided to the UE device,wherein the remote server does not provide any transmission grantoutside of the grant window; verify that the transmission grant fallswithin the grant window; and provide, based on a verification that thetransmission grant falls within the grant window, the transmission grantto the UE device.
 19. The system of claim 18, wherein: the cancellationwindow is associated with a monitoring occasion that is associated withthe UE device; the cancellation window includes a starting point at atime T₁ following an ending point of the monitoring occasion, the timeT₁ being based on a time needed by the UE device to process acancellation of the transmission grant.
 20. The system of claim 19,wherein the grant window includes an ending point at a time T₂ before astarting point of the monitoring occasion, the time T₂ being based on atime needed by the UE device for processing the transmission grant. 21.The system of claim 19, wherein the remote server is configured toreceive an indication of the time T₂ from the UE device.
 22. The systemof claim 17, wherein: the transmission is a first transmission; thetransmission grant is a first transmission grant; and the remote serveris further configured to: verify that there is a cancellation indicationthat overlaps the particular time; and not provide, based on averification that there is the cancellation indication that overlaps, asecond transmission grant for a second transmission to the UE device.23. The system of claim 22, wherein the particular time is acancellation window that is associated with a monitoring occasion thatis associated with the UE device.
 24. A cancellation monitoring logicsection of a user equipment (UE) device, wherein the cancellationmonitoring logic section is configured to: determine whether there is notransmission that overlaps with a cancellation window associated with amonitoring occasion; and based on a determination that there is notransmission that overlaps with the cancellation window, skip themonitoring occasion.
 25. The cancellation monitoring logic section ofclaim 24, wherein the cancellation monitoring logic section isconfigured to cause the UE device to not expend any processing cycles ofthe UE device doing any monitoring for a cancellation indication duringthe monitoring occasion.
 26. The cancellation monitoring logic sectionof claim 24, wherein the cancellation monitoring logic section isconfigured to: infer, by the cancellation indication monitoring logicsection of the UE device, that the transmission grant will not bereceived whose ending point is later than a time T₂ before a startingpoint of the monitoring occasion, the time T₂ being based on a timeneeded by the UE device for processing the transmission grant; and basedon an inference that the transmission grant will not be received whoseending point is later than the time T₂ before the starting point of themonitoring occasion, skip the monitoring occasion.
 27. The cancellationmonitoring logic section of claim 24, wherein: an ending point of thecancellation window is based on a period “P” of the monitoring occasion;and a length of the cancellation window is equal to the period “P” ofthe monitoring occasion.